This skill should be used when the user asks about "tech direction", "architecture", "code patterns", "technical vision", "code quality", "module structure", "file organization", "code splitting", "architecture decisions", "technical debt", "performance patterns", or discusses establishing or reviewing technical direction. Provides architecture framework for code coherence.
5.5
Rating
0
Installs
Backend Development
Category
Strong architectural guidance skill with clear triggers and comprehensive coverage of technical decision-making. The description effectively signals when to use this skill (architecture, patterns, tech debt, etc.). Provides concrete frameworks including ADR templates, module organization patterns, file size limits with enforcement rules, and domain-specific constraints (ZX rollback/memory). Structure is good with logical sections, though it packs substantial detail into SKILL.md while referencing external files that could contain some of this content. Novelty is moderate - while useful for maintaining consistency, much of this could be handled by a CLI agent with good prompting, though the file size monitoring and splitting guidance adds value. The skill effectively reduces token cost for recurring architecture discussions and ensures consistent technical decisions across a project.
majiayu000
Skill Author
Loading SKILL.md…
